This chapter provides a listing of the built-in error strings that can appear before, during and after an installation or removal using Installer 4.0.
Message Area Strings
The messages discussed in this section appear in the Installer's Message Area. These messages let the user know that specific problems have been encountered which must be addressed for the installation or removal to begin. In some cases, the Installer notifies the user why the installation cannot proceed to the designated target disk. These messages are pretty much self explanatory, however, additional explanations are presented below.
1. Message: The Installer cannot create files on the disk named “^0” because you do not have write access. Please click Select Folder to choose a different destination folder or insert a floppy disk.
The user doesn’t have write permission to the root level of the target volume. This might be the case when installing onto an AppleShare volume or UNIX volume.
2. Message: Please insert the disk you wish to install on.
The installation is taking place on a single floppy system, and the user has clicked on the Eject Disk button to eject the Installer disk.
3. Message: The selected disk named “<DiskName>” is locked. Click Switch Disk to choose a different disk.
A locked hard drive or perhaps some third-party locked medium has been selected. To replicate, use Apple HD SC Setup to lock a volume and try to perform an installation on it. A CD-ROM disk or perhaps a locked Syquest disk will also produce this message.
4. Message: The selected disk named “<DiskName>” is locked. Click Eject Disk, unlock the disk then reinsert; or click Switch Disk to choose a different disk.
The Installer cannot write to a locked floppy disk.
5. Message: The selected disk named “<DiskName>” is not an HFS volume. The Installer cannot install on volumes without the hierarchical file system. Please click Switch Disk to choose a different disk or insert a floppy disk.
The Installer cannot install to an unlocked MFS 400K floppy disk.
6. Message: The selected disk named “<DiskName>” is a network server volume. The Installer cannot install on network server volumes. Please click Switch Disk to choose a different disk or insert a floppy disk.
The Installer cannot install software to a mounted AppleShare volume unless the preference flag has been set to allow this.
7. Message: The Installer needs to use the folder named “^1” on the selected disk named “^0”, but a file with this name already exists. Please rename this file or move it to another folder.
A file with the same name as a folder that must be created during the installation. For example, place file named “Control Panels” into the System Folder, then try to install one or more Control Panels into the System Folder.
8. Message: The selected disk named “<DiskName>” is damaged. Please click Switch Disk to choose a different disk.
This message is only shown if none of the above messages apply. Normally, this error should never appear.
9. Message: An installation cannot be performed on the system disk named “^0”. Please hold down the Option key while clicking Select Disk to choose a different system disk.
The destination folder’s volume is OK, but the currently selected System Disk is not OK. The Installer will normally try hard not to let this happen by changing the currently selected System Disk to a volume that can be installed onto. This is only relevant in Folder mode.
Installer Information Alerts
The messages discussed in this section appear in the standard Macintosh Alert dialog to inform the user that some normal event has occurred and to take some next step of action.
1. Message: Installation was successful. If you are finished, click Quit to leave the Installer. If you wish to do additional installations, click Continue.
The installation was successful and does not require a system reboot because either no files were placed in the active System Folder, or the scriptwriter did not not force a restart after updating files in the active System Folder.
2. Message: Removal was successful. If you are finished, click Quit to leave the Installer. If you wish to do additional installations or removals, click Continue.
This message occurs upon successful removal of software that does not require a system reboot. Similar to the install message above.
3. Message: Installation was canceled, leaving your disk untouched.
This message occurs when the user clicks the Cancel button in the Status Dialog after clicking Install or when pressing Command-Period while the “Preparing to Install” dialog is showing.
4. Message: There was nothing to remove.
This message occurs when the user goes to the performs a software removal on a volume which does not have the designated software to remove. Action Atoms that fire on removal will prevent this message from appearing and will present the standard “Removal was successful” message.
5. Message: Installation was successful. You must now restart your Macintosh to use your new software.
This message appears when the scriptwriter has forced a restart (using the forceRestart flag in the ‘inpk’) after successful installation of software into the active System Folder.
6. Message: Removal was successful. You must now restart your Macintosh.
This message appears when the scriptwriter has forced a restart (using the forceRestart flag in the ‘inpk’) after successful removal of software from the active System Folder.
7. Message: The Installer tried to quit all other running applications, but this was canceled. Therefore, installation was canceled, leaving your disk untouched.
When running under System 7 or newer, the user has canceled the quitting of an open application while in the process of doing a live install and closing down open applications.
8. Message: The Installer tried to quit all other running applications, but this was canceled. Therefore, the removal was canceled, leaving your disk untouched
When running under System 7 or newer, the user has canceled the quitting of an open application while in the process of doing a live removal and closing down open applications.
9. Message: No installation was necessary.
After clicking the Install button it has been determined that nothing needs to be installed. This might happen if the script is only updating one file and the “keepExisting” flag in the File Atom is being used.
10. Message: Please wait while the Installer gets ready to continue….
This alert appears when the user decides to continue to perform another installation after successfully installing if the Installer had to purge script resources to make more memory free.
Installer Error Alerts
The messages discussed in this section appear in the standard Macintosh Alert dialog. These messages alert the user that some problem has occurred. The Installer may indicate a course of action to take. At present, a complete list of possible causes is not available. As new reasons for these errors become known, they will be included in this list.
1. Message: Please insert the disk “<DiskName>”.
This alert tells the user which disk to insert during the installation. The Installer will eject a disk to make room to insert the disk if necessary.
2. Message: The Installer document “<InstDoc>” requires version "<InstVers>" of the Installer application. Try opening the Installer application that is in the same folder as this Installer document.
The installation script includes an 'invs' resource which specifies the exact version of the Installer to use. The version of the Installer opened does not match the script's 'invs' resource. One cause of this alert is that there exists another version of the Installer in the Finder's application database, and the user launched the script instead of the Installer application.
3. Message: You do not have the necessary privileges to access all of the files needed on the server. Contact your network administrator.
The user is installing from a Network folder and does not have the necessary access privileges to all of the required folders. As specified in the alert message, the user needs to contact the AppleShare administrator to set folder privileges appropriately.
4. Message: An AppleShare volume has unexpectedly disappeared. The installation cannot continue.
The user was installing from the network and the network connection became broken. The user needs to contact the network administrator to have the connection problem diagnosed.
5. Message: A necessary volume has unexpectedly disappeared. Please quit the Installer and try again.
The user was installing from the network and either the Installer script's or Installer's volume has disappeared.
6. Message: The disk is locked.
The alert occurs only on an installation to a 'Floppy only' CPU. Between the switching of the source and target disks, the user has locked the target disk.
7. Message: There is not enough space on the disk “^3” to complete the installation (^0K needed, ^1K available). Remove some items from the disk “^3” and try again. Instead, you could try installing on another disk.
This message occurs when there is insufficient disk space to perform the installation. In this case, the user is not installing into the current active System Folder.
8. Message: To ensure safe removal from the active startup disk “^3” ^1K of free disk space is required (^0K available).\n\nPlease remove some files using the Finder and try again.
This message occurs when there is insufficient disk space to remove files from the active System Folder. This sounds weird, but the Installer can not delete resources from active files, or files that are currently active. (51)
9. Message: The file “<FileName>” already on “<DiskName>” is more recent than what you are about to install. Click Continue to replace “<FileName>” with the older version. Click Cancel to leave the disk “<DiskName>”untouched.
The 'infa' updateEvenIfNewer flag has been set for this file. During the installation, the Installer has found that the creation date/time value or version number for the file to be replaced, is more recent than the date/time value or version number in the source file’s ‘infs’ script resource.
10. Message: The file “<FileName>” already on “<DiskName>” is newer than what you are about to install. Click Newer to keep the newer file, Older to replace that file, or Cancel to leave the disk “<DiskName>”untouched.
The 'infa' leaveAloneIfNewer flag has been set for this file. During this custom installation, the Installer has found that the creation date/time value or version number for the file to be replaced is more recent than the date/time value or version number in the source file’s ‘infs’ script resource. No alert is presented when this situation occurs while performing an Easy Installation.
11. Message: “<DiskName>” is the wrong disk. To finish the installation, click Continue and insert “<DiskName>”. To stop any further installation, click Stop.
The user has been prompted to insert a specific disk, and has inserted the wrong disk.
12. Message: System Software is required for this installation but is not present on “<DiskName>”. Click OK, then install System Software before or as part of this installation.
The Installer script is trying to install a resource or font into a “System” file, but the file does not exist. The file is required as the “tgtRequired” flag is set in the atom.
13. Message: There were files missing on “<DiskName>” that are required for this installation. Quit the Installer and check your manual to see what is required.
The Installer script is trying to install resources or fonts into several files, but the files do not exist and must because the “tgtRequired” flag is set in the atoms.
14. Message: A file is missing from “<DiskName>” but is required for this installation. Quit the Installer and check your manual to see what files are required and how to get these files.
The Installer script is trying to install resources or fonts into a file, but the file does not exist and must because the “tgtRequired” flag is set in the atom. The name of the file is unknown or is zero length.
15. Message: The file “<FileName>” is missing on “<DiskName>” but is required for this installation. Quit the Installer and check your manual to see how to get that file.
The Installer script is trying to install resources or fonts into the specified file, but the file does not exist and must because the “tgtRequired” flag is set in the atom.
16. Message: The Installer found ^0 Installer documents on the disk “^1”. Please open the specific document you wish to use.
There are multiple Installer scripts on the installer disk, and the Installer does not know which one to open. The user can click Choose to pick a specific script file to open using Standard File.
17. Message: Installation was stopped before it was completed. The partially installed software may not be usable.
This alert is presented after the user has decided to stop the installation and the Installer did not save all original files. Important files and resources may have been deleted when the user decides to stop an installation.
18. Message: The Installer did not find any Installer documents and cannot run without one. Please open the Installer document you wish to use.
There is no Installer script for the Installer to open, but the user can click Choose to pick a specific script file to open using Standard File.
19. Message: “<DiskName>” has the correct name but is not the correct disk. Click Continue, then try inserting a different disk with this name. Or click Stop to stop any further installation.
The Installer was unable to find some file which the designated disk was supposed contain. Some possible causes: 1. A file name on the disk has been modified by having a space character appended to the end of the file name. 2. The contents of the disk are different than those specified by the Installer script. This second problem can occur if a user tries to update an Installer disk set by replacing an existing file with a more recent version. When the Installer has the creation date/time setting stored for a file in the script, and that time stamp does not match that of the source file, the Installer reports this error. 3. A final cause is that a user has tried to set up a network installation on a Novell server running Netware 2.x or earlier. See Appendix A for a discussion of this problem.
20. Message: This is not the correct “<SrcDisk>” disk. Make sure you are using the original Installer disks and try again. Click Continue if you have the correct disk to insert. Click Stop to stop any further installation.
The Installer found that some source file on that disk had a creation date which was different than that stored in the Installer script. The creation date is only important if a non-zero value is filled into the creation date field of the source 'infs' file specification resource. The developer can tell the Installer to bypass this check by placing a zero in the creation date field in the 'infs' file specification resource.
21. Message: Stopping now may result in an incomplete set of software on “<DiskName>”. Click Resume to continue the installation or Stop if you are sure you want to stop.
This alert message occurs when the user clicks the Stop button during an installation. The Stop appears in the Status Dialog when the Installer could not save all original files (due to lack of disk space) and cannot fully restore the disk to its original state.
22. Message: Installation on the active startup disk “<DiskName>”cannot take place while another application is running. Quit the Installer, then quit “<AppName>”, then try again.
This alert occurs under System 6.0.x or earlier when the installation will update files in the active System Folder and the Installer detects that there is one other application running under MultiFinder and the Installer cannot shut down the specific process for the user.
23. Message: Installation on the active startup disk “<DiskName>”cannot take place while other applications are running. Quit the Installer, then quit all running applications, then try again.
This alert occurs under System 6.0.x or earlier when the installation will update files in the active System Folder and the Installer detects that there are multiple applications open under MultiFinder.
24. Message: Installation on the active startup disk “<DiskName>” cannot take place while other applications are running. Click Continue to automatically quit all other running applications. Click Cancel to leave the disk “<DiskName>” untouched.
This alert occurs under System 7.0 when the installation will update files in the active System Folder, and the Installer detects that there are open applications other than the Finder or background processes.
25. Message: There is not enough space on the active startup disk “<DiskName>”to do this installation (<#> K available). To install on this disk you will need ^1K free.
This message occurs when there is insufficient disk space to perform the installation. When installing into the active System Folder, the Installer takes additional steps to guarantee disk integrity should the installation be canceled or aborted for whatever reason.
For example, to install a 100 byte 'adbs' resource to the System file, the Installer moves the System file to the temporary folder in the System folder, then makes a copy back in the original location. The installation occurs on the copied (and currently non-opened) System file. If a problem occurs, or the users cancels the installation, the copied file is deleted, and the System file in the temporary folder restored. If the installation is successful, the Installer places a Cleanup INIT which deletes the temporary folder and it's contents at startup. Adding a 100 byte resource, may require 2M or greater of hard disk memory on the boot volume. For this reason, it is difficult to perform an installation of some System resource to a boot floppy. If the target volume is not a boot volume, these precautions are not performed.
26. Message: Removal from the active startup disk “^3” cannot take place while other applications are running. Click Continue to automatically quit all other running applications. Click Cancel to leave your disk untouched.
This alert occurs under System 7.0 when the removal will update files in the active System Folder, and the Installer detects that there are open applications other than the Finder or background processes. (59)
27. Message: That disk is unreadable.
A floppy disk inserted during an Installer switch disk alert, was unreadable.
28. Message: An error occurred while trying to complete the installation. Installation was canceled, leaving your disk untouched.
This alert results when a resource problem occurs during a live install. The Installer makes frequent checks of ResError during it's processing. It may encounter a spurious error set by some background process which gets interpreted as an unresolved Installer failure.
The error has been found to occur with INITs which patch GetNextEvent in order to process specific system events. If this alert occurs, users should be advised to reboot their system with the shift key held down under System 7.0, or to manually remove any suspect INIT's or other startup documents under System 6.0.x and prior.
29. Message: The Installer needs to modify the file named “^0” on the disk “^3” but that file is locked. Please unlock the file and try again.
Depending on the scriptwriter’s wishes, the Installer will not overwrite locked files. Unfortunately, if several files are locked, this alert occurs for each locked file.
30. Message: The Installer found an alias named “<AliasName>” but could not find the original Installer document to which this alias points. Make sure you are using the original Installer disks.
An alias to an Installer script can be used in place of the actual document when using floppy disks. If the alias cannot be resolved, this alert occurs.
31. Message: Installer documents cannot be printed. Quit the Installer and open the document to do an installation.
The user has tried to print the document using the Finder. The Installer may or may not already be running.
32. Message: The files needed for this installation could not be found on your server volume "<VolName>". Please contact your network administrator about this problem.
This error occurs when a network installation is run, and an error occurs accessing the source files. For example move some of the necessary files from the network installation folder, and attempt the installation.
33. Message: Problems were encountered deleting old files. Please quit the Installer, restart your Macintosh and try running the Installer again.
This problem occurs when the Installer is unable to modify a target document. On a non-boot volume installation, an open application may have some file opened which is targeted for replacement by the installation. For example use ResEdit to open the System file on a non-boot volume, and try to install system software to that volume.
34. Message: The Installer document “<InstDoc>” is unusable for installation. An error was detected before installation began. Make sure you are using the original Installer disks.
This error occurs when the Installer is unable to find a required resource specified in the installer script - 'inrl', 'inpk', 'infa', etc., has become corrupted, or the resource map has become corrupted.
This error has also been known to occur due to the following reasons.
1. Two packages are included for installation which involve conflicting actions. One package calls for the installation of a file or resource, and the other package calls for it's deletion, if it exists.
2. The same source resource is specified for installation as two different resources under separate resource ID's. In other words, there are 2 'inra' resource which reference the same source resource, but specify different target resources.
35. Message: A disk error has occurred and installation cannot continue. Your disk may be damaged.
This error occurs when the Installer and/or script file are placed on an MFS formatted diskette, and are used from that diskette.
36. Message: The Installer needs to create a folder named “<FolderName>” on the disk “<DiskName>” but a file with this name already exists. Please rename this file or move it to another folder.
The Installer is unable to create some folder because a file exists by that name in the specified locations.
37. Message: The file “<FileName>” on disk “<DiskName>”cannot be replaced by the Installer. No installation will take place. Please move the file to another folder and try again.
This alert is related to the previous error except that a folder by the same name as that of the file exists on the target pathname and cannot be replaced.
Another reason for this error is when the creation date/time field for the target (not source) file specification resource, 'infs' is non-zero AND the file already exists in the specified location. The Programmer's Guide indicates that the creation date/time field should be zero. In fact, it must be set to zero, otherwise this alert occurs when trying to perform a second installation to a target hard disk.
This error also occurs if the target file specification has specified "typeCrMustMatch" and the type and creator of the actual target file do not match the specified values in the target file specification.
38. Message: The Installer cannot copy the file “<FileName>” onto the disk “<DiskName>” Installation cannot continue. Please delete this file and try running the Installer again.
This error occurs when the Installer runs into problems copying a target file, but not for the reason that a folder exists by the same name as the file. Instead, the file copy process has already begun, however, it cannot be completed.
One unusual situation which can lead to this problem occurs when one user sets up a network installation and turns personal file sharing on. A second user then turns on personal file sharing then mounts the first users server with administrator, while the first user mounts the second users volume. The second user launches the network installation to install software onto his volume. If the first user can lock a newly created file on the second users disk while the Installer is creating the file, this alert results.
39. Message: “<FileName>” cannot run on this model of Macintosh. Please contact your authorized Apple dealer and inquire about upgrading your hardware. Click Quit to leave the Installer.
This error occurs when trying to use the Installer on a 128K or 512K Mac. Installer 3.4 is not compatible with these Systems.
40. Message: The Installer document “<InstDoc>” is damaged. Make sure you are using the original Installer disks and try again.
The script document cannot be opened by the Installer. This error can result given a network installation when the administrator launches the script locally, then a user accesses the script from a workstation and tries to run the script using a remote copy of the Installer. The workstation Installer will receive this alert message.
Another possible reason is that not enough memory is available to load the script into the Installer’s heap. Try raising the Installer’s partition if the script is large.
41. Message: An error occurred while removing. Removal was not able to be completed, but your original software has been restored.
An unspecified error occurred while doing software removal from the boot-disk. The error can occur from incompatible startup documents or INIT's. To overcome, reboot the system with the shift key held down under System 7.0 or greater, or remove all extraneous startup documents and INITs and reboot under System 6.0.x and earlier.
42. Message: An unknown error #"<Error #>" has occurred.
This is a catch all error alert which appears when an error occurs during some phase of installation which the Installer cannot sort out. The two common error numbers are 2231 and 2232. Error 2231 indicates that some resource file could not be found. Error 2232 indicates that a specific resource could not be found. Both of these errors have been found to occur as a result of incompatible startup documents or INITs. The Installer makes frequent checks of ResError and may encounter a spurious error set by some background process which gets interpreted as an unresolved Installer failure.
The error has been found to occur with INITs which patch GetNextEvent in order to process specific system events. If this alert occurs, users should be advised to reboot their system with the shift key held down under System 7.0, or to manually remove any suspect INIT's or other startup documents under System 6.0.x and prior.
43. Message: A clean install cannot be performed on the disk “<DiskName>”.
This error is displayed when trying to setup a clean install using the Command-Option-K keys, when a clean install is inappropriate. This might be because: no blessed folder exists on the target disk, the preference flag is set to not allow clean installs, or an internal error occurred while setting up the clean install. (18)
44. Message: There are too many desk accessories on “^3” to complete this installation. Installation would result in ^0 desk accessories; only ^1 are allowed. Remove some desk accessories, and try again.
When installing a desk accessory as a ‘DRVR’ resource in the System this error is displayed if all DA driver slots are taken. (26)
45. Message: The disk “^0” could not be ejected because it is being shared. Please turn off file sharing and try the installation again.
The Installer displays with error when trying to eject a CD-ROM to make room for the user to insert another CD-ROM, but the File Manager returned an error when calling Eject. (48)
46. Message: Installer documents cannot be opened while the Installer is running. Please quit the Installer and open the document again.
The user has tried to open the document using the Finder while the Installer is running. Installer documents can only be opened when launching the Installer. (78)
47. Message: The file “^0” on the disk “^3” is too large to accommodate the installation. The installation cannot continue. Try removing “^0” and installing again.
The script is adding resources or fonts to a file whose resource fork will exceed the 16Mb size limit. This was a real issue when installing Kanji fonts into the System file, but shouldn’t happen as often with separate font suitcases. (79).
48. Message: The installation cannot continue because the source file “^0” on the disk “^1” will be overwritten during the installation. Please choose a different installation disk and try again..
The Installer will write over a file that is part of the installation sources. For disk mode only. (80)
49. Message: The installation cannot continue because the source file “^0” on the disk “^1” will be overwritten during the installation. Please select a different installation folder and try again.
The Installer will write over a file that is part of the installation sources. For folder mode only. (81)
50. Message: The removal cannot continue because the source file “^0” on the disk “^1” will be deleted during the removal. Please choose a different target disk and try again.
The Installer will delete a file that is part of the installation sources. For disk mode only. (82)
51. Message: The removal cannot continue because the source file “^0” on the disk “^1” will be deleted during the removal. Please select a different target folder and try again.
The Installer will delete a file that is part of the installation sources. For folder mode only. (83)
52. Message: Cannot overwrite a protected resource in the file “^0” on the disk “^3”. Error detected before installation began.
A resource specified for replacement on the target disk has the protected bit set. The protected bit needs to be cleared before the installation can proceed.
53. Message: The selected disk is too full. Please remove some files you no longer need.
This problem can occur when the target volume is being shared via File Sharing. If an installation is started and a user logs onto the same disk and copies additional data to the server after the Installer preflight has taken place, the target disk may run out of hard disk space resulting in this error.
Other Installer Error Alerts
The following Installer Alert messages can appear during an installation. Where possible, troubleshooting is provided. Unfortunately, comprehensive information is not available at this time.
1. Message: There is a problem with the source disk “^0”. Installation cannot continue. The partially installed software may not be usable. Make sure you are using the original Installer disks.
The Installer received a Resource Manager error while trying to read from a source file. This error has been found to occur with INITs which patch GetNextEvent in order to process specific system events. If this alert occurs, users should be advised to reboot their system with the shift key held down under System 7.0, or to manually remove any suspect INIT's or other startup documents under System 6.0.x and prior.
2. Message: A problem occurred with the AppleTalk network. Please quit the Installer, restart your Macintosh, and try running the Installer again.
The network connection may have gone down while performing a network installation.
3. Message: A necessary file is locked. Installation cannot continue.
The Installer received the File Manager error -54 or -45 while opening a target file. Most likely, something or someone locked a target file during the installation.
4. Message: There are too many files open on your Macintosh. Please quit the Installer, quit any other applications you may be running, and try again.
The Installer received the File Manager error -42 while opening a file. This might be the case if another application has numerous files open, that would cause the Installer to reach the maximum number of files that can be open at once. Try using up all but two FCBs then performing a non-live installation.
5. Message: There is a problem with the source disk “^0”. No installation can take place. Make sure you are using the original Installer disks.
The Installer received an error while examining the first source disk.
6. Message: “<Installer>” cannot run on your version of Macintosh Software. Please restart your Macintosh using your original set of distribution disks. Click Quit to leave the Installer.
The Installer must have System 4.1 or higher to run. This error occurs with System 3.2 and earlier.
7. Message: The Installer cannot be opened from an MFS disk. Click Quit, then open a copy of the Installer from a disk that supports the hierarchical file system.
The Installer can only be used from an HFS volume.
8. Message: An error occurred while trying to complete the installation.
An Action Atom has returned a result signifying that an error occurred during execution of the Action Atom.
9. Message: This copy of the Installer seems to be damaged. Make sure you are using the original Installer disks.
The Installer has been damaged in some way. This error can be replicated by using ResEdit to remove some of its resources.
10. Message: There has been a problem with the file server. Perhaps you do not have the necessary privileges. Check with your network administrator.
The user may not have sufficient network privileges to the AppleShare volume on which the network installation is located.
11. Message: A needed file is already in use or was left open.
We may display this error if we get a -47 or -49 File Manager error back from our Target File routines. This error my be converted into a more generic error.
12. Message: The Installer needs more memory to perform an installation. Try quitting other applications and running the Installer again. You could also try removing some system extensions and restarting to make more memory available.
We display this error when the Memory Manager returns an error from -117 to -108. Depending on where we run out of memory, we’ll display this error if the Installer’s partition is too low. The original intention of this error was to handle the case where we were running on a 1Mb Mac running 6.0.X with single Finder. This continues to be a possible scenario, but is less likely than several years ago. (7)
13. Message: One of your disks is no longer available. Please quit the Installer, restart your Macintosh, and try running the Installer again.
We may display this error when the File Manager returns an error of -53. This error may be converted into a more generic error. (10)
14. Message: There is a problem with a disk you are installing onto. No installation can take place. Try installing onto another disk.
Resource Manager errors were returned during opening, reading or writing a target resource or font. Most likely, the target file’s resource fork is corrupted. (47)
» d ˇ ˇˇˇˇ d
_ , Times
. +61Installer 4.0.3 * Error Guide
$ ( 6
+ ®
(Ë 6)Document Version 1.3 - February 17, 1994 ˇé d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ú ~Table of Contents , Palatino (Ú ii , Times
° d ONLN d L 6 d ‰ ( ^ 6Table of Contents
° d ONLN d Ö 6 óD *5"Installer Error And Message Alerts " ° ∂ ó 4 ó+ ° ∂ ° ∂
° d ONLN d 5 ò 6 § ó *Message Area Strings ° d ONLN dˇˇ )c ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )`........................... ° d ONLN dˇˇ ( ° ó ° d ONLN d J ò
§ ( °
3 ° d ONLN d L § 6 ∞ µ ( ≠ 6 Installer Information Alerts ° d ONLN dˇˇ )Å ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )`................. ° d ONLN dˇˇ ( ≠ µ ° d ONLN d i §
∞ ( ≠
4 ° d ONLN d k ∞ 6 º ñ ( π 6Installer Error Alerts ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ............................ ° d ONLN dˇˇ ( π ñ ° d ONLN d Ç ∞
º ( π
5 ° d ONLN d Ñ º 6 » ¥ ( ≈ 6 Other Installer Error Alerts ° d ONLN dˇˇ )~ ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )` ................................ ° d ONLN dˇˇ )`.................. ° d ONLN dˇˇ ( ≈ ¥ ° d ONLN d ° º
$ ° d ONLN d L ~ t¨ ( j ~Installer Error And ° d ONLN d t ~ ú~ *(Message Strings " ° ∂ < 4<+ ° ∂ ° ∂
° d ONLN d $A ~M# *∏`This chapter provides a listing of the built-in error strings that can appear before, during and ° d ONLN d ÖM ~Yc * 5after an installation or removal using Installer 4.0.
° d ONLN d ªq 6Ö Í (Ä 6Message Area Strings " ° ∂ Ö 4Ö+ ° ∂ ° ∂
° d ONLN d –ä ~ñ' +H^The messages discussed in this section appear in the Installer's Message Area. These messages ° d ONLN d/ñ ~¢ * Zlet the user know that specific problems have been encountered which must be addressed for ° d ONLN dä¢ ~Æ * ]the installation or removal to begin. In some cases, the Installer notifies the user why the ° d ONLN dËÆ ~∫( * _installation cannot proceed to the designated target disk. These messages are pretty much self ° d ONLN dH∫ ~Δ∂ * Bexplanatory, however, additional explanations are presented below. ° d ONLN d㌠~⁄ Ü *1. ° d ONLN déŒ ê⁄ ∂ )Message ° d ONLN dïŒ ∂⁄" )&R: The Installer cannot create files on the disk named “^0” because you do not have ° d ONLN dË⁄ êÊ" („ ê^write access. Please click Select Folder to choose a different destination folder or insert a ° d ONLN dGÊ êÚ » * floppy disk. ° d ONLN dW˙ ê# *ZThe user doesn’t have write permission to the root level of the target volume. This might ° d ONLN d≤ ê⁄ * Ebe the case when installing onto an AppleShare volume or UNIX volume. ° d ONLN d¯ ~& Ü (# ~2. ° d ONLN d˚ ê& ∂ )Message ° d ONLN d ∂&É )&0: Please insert the disk you wish to install on. ° d ONLN d4. ê:# (7 ê[The installation is taking place on a single floppy system, and the user has clicked on the ° d ONLN dë: êFQ * .Eject Disk button to eject the Installer disk. ° d ONLN d¿N ~Z Ü (W ~3. ° d ONLN d√N êZ ∂ )Message ° d ONLN d N ∂Z& )&N: The selected disk named “<DiskName>” is locked. Click Switch Disk to choose ° d ONLN dZ êf ⁄ (c êa different disk. ° d ONLN d,n êz *TA locked hard drive or perhaps some third-party locked medium has been selected. To ° d ONLN dÅz êÜ( * [replicate, use Apple HD SC Setup to lock a volume and try to perform an installation on it. ° d ONLN dfiÜ êí * NA CD-ROM disk or perhaps a locked Syquest disk will also produce this message. ° d ONLN d-ö ~¶ Ü (£ ~4. ° d ONLN d0ö ê¶ ∂ )Message ° d ONLN d7ö ∂¶# )&O: The selected disk named “<DiskName>” is locked. Click Eject Disk, unlock the ° d ONLN dᶠê≤∏ (Ø êDdisk then reinsert; or click Switch Disk to choose a different disk. ° d ONLN dœ∫ êΔs *3The Installer cannot write to a locked floppy disk. ˇX d ˇ ˇˇˇˇ d
° d ONLN d L ~ X Ü ( U ~5. ° d ONLN d L ê X ∂ )Message ° d ONLN d
L ∂ X )&K: The selected disk named “<DiskName>” is not an HFS volume. The Installer ° d ONLN d V X ê d# ( a êYcannot install on volumes without the hierarchical file system. Please click Switch Disk ° d ONLN d ∞ d ê pk * 3to choose a different disk or insert a floppy disk. ° d ONLN d „ x ~ Ñ Ä ( Å ~ ° d ONLN d Á x ê Ñ∏ )AThe Installer cannot install to an unlocked MFS 400K floppy disk. ° d ONLN d) å ~ ò Ü ( ï ~6. ° d ONLN d, å ê ò ∂ )Message ° d ONLN d3 å ∂ ò )&G: The selected disk named “<DiskName>” is a network server volume. The ° d ONLN d{ ò ê § ( ° êYInstaller cannot install on network server volumes. Please click Switch Disk to choose a ° d ONLN d’ § ê ∞8 * 'different disk or insert a floppy disk. ° d ONLN d˛ ∏ ê ƒ˛ *OThe Installer cannot install software to a mounted AppleShare volume unless the ° d ONLN dN ƒ ê –L * +preference flag has been set to allow this. ° d ONLN dz ÿ ~ ‰ Ü ( · ~7. ° d ONLN d} ÿ ê ‰ ∂ )Message ° d ONLN dÑ ÿ ∂ ‰' )&S: The Installer needs to use the folder named “^1” on the selected disk named “^0”, ° d ONLN dÿ ‰ ê ( Ì êXbut a file with this name already exists. Please rename this file or move it to another ° d ONLN d1 ê ¸ Ø * folder. ° d ONLN d: ê *XA file with the same name as a folder that must be created during the installation. For ° d ONLN dì ê & * Zexample, place file named “Control Panels” into the System Folder, then try to install one ° d ONLN dÓ ê(a * .or more Control Panels into the System Folder. ° d ONLN d 0 ~< Ü (9 ~8. ° d ONLN d 0 ê< ∂ )Message ° d ONLN d'0 ∂<$ )&L: The selected disk named “<DiskName>” is damaged. Please click Switch Disk ° d ONLN dt< êH (E êto choose a different disk. ° d ONLN dëP ê\ *UThis message is only shown if none of the above messages apply. Normally, this error ° d ONLN dÁ\ êh * should never appear. ° d ONLN d¸p ~| Ü (y ~9. ° d ONLN dˇp ê| ∂ )Message ° d ONLN dp ∂|' )&R: An installation cannot be performed on the system disk named “^0”. Please hold ° d ONLN dY| êà (Ö êQdown the Option key while clicking Select Disk to choose a different system disk. ° d ONLN d¨ê êú *XThe destination folder’s volume is OK, but the currently selected System Disk is not OK. ° d ONLN dú ê® * UThe Installer will normally try hard not to let this happen by changing the currently ° d ONLN d\® ê¥ * Vselected System Disk to a volume that can be installed onto. This is only relevant in ° d ONLN d≥¥ ê¿ À * Folder mode.
° d ONLN d¿ÿ 6Ï (Á 6 Installer Information Alerts " ° ∂ Ï 4Ï+ ° ∂ ° ∂
° d ONLN d›Ò ~˝ +HWThe messages discussed in this section appear in the standard Macintosh Alert dialog to ° d ONLN d5˝ ~ * Yinform the user that some normal event has occurred and to take some next step of action. ° d ONLN dè ~ Ü *1. ° d ONLN dí ê π )Message: ° d ONLN dö π & ))V Installation was successful. If you are finished, click Quit to leave the Installer. ° d ONLN dÚ ê)î (& ê;If you wish to do additional installations, click Continue. ° d ONLN d/1 ê=$ *\The installation was successful and does not require a system reboot because either no files ° d ONLN då= êI * Xwere placed in the active System Folder, or the scriptwriter did not not force a restart ° d ONLN dÂI êUk * 1after updating files in the active System Folder. ° d ONLN d ] ~i Ü (f ~2. ° d ONLN d ] êi ª ) Message: ° d ONLN d #] ªi$ )+TRemoval was successful. If you are finished, click Quit to leave the Installer. If ° d ONLN d xi êu¡ (r êDyou wish to do additional installations or removals, click Continue. ° d ONLN d ø} êâ *VThis message occurs upon successful removal of software that does not require a system ° d ONLN d
â êï\ * .reboot. Similar to the install message above. ° d ONLN d
° d ONLN d L ~ X Ü ( U ~4. ° d ONLN d L ê X ª ) Message: ° d ONLN d L ª X@ )+ There was nothing to remove. ° d ONLN d * ` ê l ( i êUThis message occurs when the user goes to the performs a software removal on a volume ° d ONLN d Ä l ê x * Qwhich does not have the designated software to remove. Action Atoms that fire on ° d ONLN d “ x ê Ñ˛ * Nremoval will prevent this message from appearing and will present the standard ° d ONLN d! Ñ ê ê. * !“Removal was successful” message. ° d ONLN dC ò ~ § Ü ( ° ~5. ° d ONLN dF ò ê § ª ) Message: ° d ONLN dO ò ª §$ )+QInstallation was successful. You must now restart your Macintosh to use your new ° d ONLN d° § ê ∞ ª ( ≠ ê software. ° d ONLN d¨ ∏ ê ƒ *WThis message appears when the scriptwriter has forced a restart (using the forceRestart ° d ONLN d ƒ ê – * \flag in the ‘inpk’) after successful installation of software into the active System Folder. ° d ONLN da ÿ ~ ‰ Ü ( · ~6. ° d ONLN dd ÿ ê ‰ ª ) Message: ° d ONLN dm ÿ ª ‰‘ )+=Removal was successful. You must now restart your Macintosh. ° d ONLN d¨ Ï ê ¯ ( ı êWThis message appears when the scriptwriter has forced a restart (using the forceRestart ° d ONLN d ¯ ê * Wflag in the ‘inpk’) after successful removal of software from the active System Folder. ° d ONLN d\ ~ Ü ( ~7. ° d ONLN d_ ê ª ) Message: ° d ONLN dh ª! )+RThe Installer tried to quit all other running applications, but this was canceled. ° d ONLN dº ê$Ω (! êBTherefore, installation was canceled, leaving your disk untouched. ° d ONLN d , ê8 *SWhen running under System 7 or newer, the user has canceled the quitting of an open ° d ONLN dT8 êDÏ * Napplication while in the process of doing a live install and closing down open ° d ONLN d£D êP Õ *
applications. ° d ONLN d±X ~d Ü (a ~8. ° d ONLN d¥X êd ª ) Message: ° d ONLN dΩX ªd! )+RThe Installer tried to quit all other running applications, but this was canceled. ° d ONLN dd êpª (m ê@Therefore, the removal was canceled, leaving your disk untouched ° d ONLN dSx êÑ *SWhen running under System 7 or newer, the user has canceled the quitting of an open ° d ONLN dßÑ êêÛ * Napplication while in the process of doing a live removal and closing down open ° d ONLN dˆê êú Õ *
applications. ° d ONLN d§ ~∞ Ü (≠ ~9. ° d ONLN d§ ê∞ ª ) Message: ° d ONLN d§ ª∞F )+ No installation was necessary. ° d ONLN d0∏ êƒ& (¡ ê\After clicking the Install button it has been determined that nothing needs to be installed. ° d ONLN déƒ ê– * XThis might happen if the script is only updating one file and the “keepExisting” flag in ° d ONLN dÁ– ê‹
* the File Atom is being used. ° d ONLN d‰ ~ ã (Ì ~10. ° d ONLN d‰ ê ª ) Message: ° d ONLN d‰ ª∫ )+8Please wait while the Installer gets ready to continue…. ° d ONLN dK¯ ê% ( êZThis alert appears when the user decides to continue to perform another installation after ° d ONLN d¶ ê * Zsuccessfully installing if the Installer had to purge script resources to make more memory ° d ONLN d ê • * free.
° d ONLN d4 6H fi (C 6Installer Error Alerts " ° ∂ H 4H+ ° ∂ ° ∂
° d ONLN d M ~Y" +H\The messages discussed in this section appear in the standard Macintosh Alert dialog. These ° d ONLN d{Y ~e' * _messages alert the user that some problem has occurred. The Installer may indicate a course of ° d ONLN d€e ~q * aaction to take. At present, a complete list of possible causes is not available. As new reasons ° d ONLN d =q ~}û * Bfor these errors become known, they will be included in this list. ° d ONLN d ÄÖ ~ë Ü *1. ° d ONLN d ÉÖ êë ª ) Message: ° d ONLN d åÖ ªël )+$Please insert the disk “<DiskName>”. ° d ONLN d ≤ô ê• (¢ ê[This alert tells the user which disk to insert during the installation. The Installer will ° d ONLN d
• ê±â * :eject a disk to make room to insert the disk if necessary. ° d ONLN d
Iπ ~≈ Ü (¬ ~2. ° d ONLN d
Lπ ê≈ ª ) Message: ° d ONLN d
Uπ ª≈ )+GThe Installer document “<InstDoc>” requires version "<InstVers>" of the ° d ONLN d
ù≈ ê—! (Œ ê[Installer application. Try opening the Installer application that is in the same folder as * this Installer document. ˇ‚ d ˇ ˇˇˇˇ d
° d ONLN dˇˇ ( U ê\The installation script includes an 'invs' resource which specifies the exact version of the ° d ONLN dˇˇ * YInstaller to use. The version of the Installer opened does not match the script's 'invs' ° d ONLN dˇˇ * _resource. One cause of this alert is that there exists another version of the Installer in the ° d ONLN dˇˇ * XFinder's application database, and the user launched the script instead of the Installer ° d ONLN dˇˇ * application. ° d ONLN dˇˇ ( ô ~3. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QYou do not have the necessary privileges to access all of the files needed on the ° d ONLN dˇˇ ( • ê,server. Contact your network administrator. ° d ONLN dˇˇ *SThe user is installing from a Network folder and does not have the necessary access ° d ONLN dˇˇ * ]privileges to all of the required folders. As specified in the alert message, the user needs ° d ONLN dˇˇ * Oto contact the AppleShare administrator to set folder privileges appropriately. ° d ONLN dˇˇ (  ~4. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KAn AppleShare volume has unexpectedly disappeared. The installation cannot ° d ONLN dˇˇ ( Ò ê continue. ° d ONLN dˇˇ *WThe user was installing from the network and the network connection became broken. The ° d ONLN dˇˇ * Yuser needs to contact the network administrator to have the connection problem diagnosed. ° d ONLN dˇˇ (% ~5. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+OA necessary volume has unexpectedly disappeared. Please quit the Installer and ° d ONLN dˇˇ (1 ê
try again. ° d ONLN dˇˇ *YThe user was installing from the network and either the Installer script's or Installer's ° d ONLN dˇˇ * volume has disappeared. ° d ONLN dˇˇ (e ~6. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+The disk is locked. ° d ONLN dˇˇ (y êZThe alert occurs only on an installation to a 'Floppy only' CPU. Between the switching of ° d ONLN dˇˇ * Athe source and target disks, the user has locked the target disk. ° d ONLN dˇˇ (ô ~7. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+LThere is not enough space on the disk “^3” to complete the installation (^0K ° d ONLN dˇˇ (• êVneeded, ^1K available). Remove some items from the disk “^3” and try again. Instead, ° d ONLN dˇˇ * )you could try installing on another disk. ° d ONLN dˇˇ *ZThis message occurs when there is insufficient disk space to perform the installation. In ° d ONLN dˇˇ * Lthis case, the user is not installing into the current active System Folder. ° d ONLN dˇˇ ( ~8. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+RTo ensure safe removal from the active startup disk “^3” ^1K of free disk space is ° d ONLN dˇˇ (Ò êUrequired (^0K available).\n\nPlease remove some files using the Finder and try again. ° d ONLN dˇˇ *YThis message occurs when there is insufficient disk space to remove files from the active ° d ONLN dˇˇ * YSystem Folder. This sounds weird, but the Installer can not delete resources from active ° d ONLN dˇˇ * 0files, or files that are currently active. (51) ° d ONLN dˇˇ (1 ~9. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+FThe file “<FileName>” already on “<DiskName>” is more recent than what ° d ONLN dˇˇ (= êYyou are about to install. Click Continue to replace “<FileName>” with the older version. ° d ONLN dˇˇ * 5Click Cancel to leave the disk “<DiskName>”untouched. ° d ONLN dˇˇ *[The 'infa' updateEvenIfNewer flag has been set for this file. During the installation, the ° d ONLN dˇˇ * ZInstaller has found that the creation date/time value or version number for the file to be ° d ONLN dˇˇ * Xreplaced, is more recent than the date/time value or version number in the source file’s ° d ONLN dˇˇ * ‘infs’ script resource. ° d ONLN dˇˇ (ï ~10. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+HThe file “<FileName>” already on “<DiskName>” is newer than what you are ° d ONLN dˇˇ (° ê\about to install. Click Newer to keep the newer file, Older to replace that file, or Cancel ° d ONLN dˇˇ * (to leave the disk “<DiskName>”untouched. ° d ONLN dˇˇ *QThe 'infa' leaveAloneIfNewer flag has been set for this file. During this custom ° d ONLN dˇˇ * Yinstallation, the Installer has found that the creation date/time value or version number ° d ONLN dˇˇ * \for the file to be replaced is more recent than the date/time value or version number in the ˇ~ d ˇ ˇˇˇˇ d
installation. ° d ONLN dˇˇ *_The Installer script is trying to install a resource or font into a “System” file, but the file ° d ONLN dˇˇ * Sdoes not exist. The file is required as the “tgtRequired” flag is set in the atom. ° d ONLN dˇˇ ( ı ~13. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+CThere were files missing on “<DiskName>” that are required for this ° d ONLN dˇˇ ( êPinstallation. Quit the Installer and check your manual to see what is required. ° d ONLN dˇˇ *aThe Installer script is trying to install resources or fonts into several files, but the files do ° d ONLN dˇˇ * Fnot exist and must because the “tgtRequired” flag is set in the atoms. ° d ONLN dˇˇ (5 ~14. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+PA file is missing from “<DiskName>” but is required for this installation. Quit ° d ONLN dˇˇ (A êWthe Installer and check your manual to see what files are required and how to get these ° d ONLN dˇˇ * files. ° d ONLN dˇˇ *_The Installer script is trying to install resources or fonts into a file, but the file does not ° d ONLN dˇˇ * Zexist and must because the “tgtRequired” flag is set in the atom. The name of the file is ° d ONLN dˇˇ * unknown or is zero length. ° d ONLN dˇˇ (ç ~15. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+IThe file “<FileName>” is missing on “<DiskName>” but is required for this ° d ONLN dˇˇ (ô êTinstallation. Quit the Installer and check your manual to see how to get that file. ° d ONLN dˇˇ *bThe Installer script is trying to install resources or fonts into the specified file, but the file ° d ONLN dˇˇ * Jdoes not exist and must because the “tgtRequired” flag is set in the atom. ° d ONLN dˇˇ (Õ ~16. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+MThe Installer found ^0 Installer documents on the disk “^1”. Please open the ° d ONLN dˇˇ (Ÿ ê"specific document you wish to use. ° d ONLN dˇˇ *[There are multiple Installer scripts on the installer disk, and the Installer does not know ° d ONLN dˇˇ * Zwhich one to open. The user can click Choose to pick a specific script file to open using ° d ONLN dˇˇ * Standard File. ° d ONLN dˇˇ ( ~17. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+JInstallation was stopped before it was completed. The partially installed ° d ONLN dˇˇ (% êsoftware may not be usable. ° d ONLN dˇˇ *]This alert is presented after the user has decided to stop the installation and the Installer ° d ONLN dˇˇ * Zdid not save all original files. Important files and resources may have been deleted when ° d ONLN dˇˇ * )the user decides to stop an installation. ° d ONLN dˇˇ (e ~18. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+NThe Installer did not find any Installer documents and cannot run without one. ° d ONLN dˇˇ (q ê3Please open the Installer document you wish to use. ° d ONLN dˇˇ *_There is no Installer script for the Installer to open, but the user can click Choose to pick a ° d ONLN dˇˇ * 1specific script file to open using Standard File. ° d ONLN dˇˇ (• ~19. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+O“<DiskName>” has the correct name but is not the correct disk. Click Continue, ° d ONLN dˇˇ (± êVthen try inserting a different disk with this name. Or click Stop to stop any further ° d ONLN dˇˇ *
installation. ° d ONLN dˇˇ *QThe Installer was unable to find some file which the designated disk was supposed ° d ONLN dˇˇ * Xcontain. Some possible causes: 1. A file name on the disk has been modified by having a ˇX d ˇ ˇˇˇˇ d
° d ONLN dˇˇ ( U êVspace character appended to the end of the file name. 2. The contents of the disk are ° d ONLN dˇˇ * [different than those specified by the Installer script. This second problem can occur if a ° d ONLN dˇˇ * [user tries to update an Installer disk set by replacing an existing file with a more recent ° d ONLN dˇˇ * Xversion. When the Installer has the creation date/time setting stored for a file in the ° d ONLN dˇˇ * Yscript, and that time stamp does not match that of the source file, the Installer reports ° d ONLN dˇˇ * \this error. 3. A final cause is that a user has tried to set up a network installation on a ° d ONLN dˇˇ * VNovell server running Netware 2.x or earlier. See Appendix A for a discussion of this ° d ONLN dˇˇ * problem. ° d ONLN dˇˇ ( Ω ~20. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+OThis is not the correct “<SrcDisk>” disk. Make sure you are using the original ° d ONLN dˇˇ ( … ê]Installer disks and try again. Click Continue if you have the correct disk to insert. Click ° d ONLN dˇˇ * &Stop to stop any further installation. ° d ONLN dˇˇ *TThe Installer found that some source file on that disk had a creation date which was ° d ONLN dˇˇ * ]different than that stored in the Installer script. The creation date is only important if a ° d ONLN dˇˇ * ]non-zero value is filled into the creation date field of the source 'infs' file specification ° d ONLN dˇˇ * ]resource. The developer can tell the Installer to bypass this check by placing a zero in the ° d ONLN dˇˇ * >creation date field in the 'infs' file specification resource. ° d ONLN dˇˇ (- ~21. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+IStopping now may result in an incomplete set of software on “<DiskName>”. ° d ONLN dˇˇ (9 êSClick Resume to continue the installation or Stop if you are sure you want to stop. ° d ONLN dˇˇ *[This alert message occurs when the user clicks the Stop button during an installation. The ° d ONLN dˇˇ * [Stop appears in the Status Dialog when the Installer could not save all original files (due ° d ONLN dˇˇ * Oto lack of disk space) and cannot fully restore the disk to its original state. ° d ONLN dˇˇ (y ~22. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KInstallation on the active startup disk “<DiskName>”cannot take place while ° d ONLN dˇˇ (Ö êSanother application is running. Quit the Installer, then quit “<AppName>”, then try ° d ONLN dˇˇ * again. ° d ONLN dˇˇ *ZThis alert occurs under System 6.0.x or earlier when the installation will update files in ° d ONLN dˇˇ * Vthe active System Folder and the Installer detects that there is one other application ° d ONLN dˇˇ * Yrunning under MultiFinder and the Installer cannot shut down the specific process for the ° d ONLN dˇˇ * user. ° d ONLN dˇˇ (› ~23. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KInstallation on the active startup disk “<DiskName>”cannot take place while ° d ONLN dˇˇ (È ê\other applications are running. Quit the Installer, then quit all running applications, then ° d ONLN dˇˇ *
try again. ° d ONLN dˇˇ *ZThis alert occurs under System 6.0.x or earlier when the installation will update files in ° d ONLN dˇˇ * Wthe active System Folder and the Installer detects that there are multiple applications ° d ONLN dˇˇ * open under MultiFinder. ° d ONLN dˇˇ (5 ~24. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+LInstallation on the active startup disk “<DiskName>” cannot take place while ° d ONLN dˇˇ (A êVother applications are running. Click Continue to automatically quit all other running ° d ONLN dˇˇ * Eapplications. Click Cancel to leave the disk “<DiskName>” untouched. ° d ONLN dˇˇ *XThis alert occurs under System 7.0 when the installation will update files in the active ° d ONLN dˇˇ * XSystem Folder, and the Installer detects that there are open applications other than the ° d ONLN dˇˇ * Finder or background processes. ° d ONLN dˇˇ (ç ~25. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KThere is not enough space on the active startup disk “<DiskName>”to do this ° d ONLN dˇˇ (ô êQinstallation (<#> K available). To install on this disk you will need ^1K free. ° d ONLN dˇˇ *VThis message occurs when there is insufficient disk space to perform the installation. ° d ONLN dˇˇ * VWhen installing into the active System Folder, the Installer takes additional steps to ° d ONLN dˇˇ * Tguarantee disk integrity should the installation be canceled or aborted for whatever ° d ONLN dˇˇ * reason. ˇ6 d ˇ ˇˇˇˇ d
° d ONLN dˇˇ ( U êZFor example, to install a 100 byte 'adbs' resource to the System file, the Installer moves ° d ONLN dˇˇ * Wthe System file to the temporary folder in the System folder, then makes a copy back in ° d ONLN dˇˇ * Xthe original location. The installation occurs on the copied (and currently non-opened) ° d ONLN dˇˇ * \System file. If a problem occurs, or the users cancels the installation, the copied file is ° d ONLN dˇˇ * Vdeleted, and the System file in the temporary folder restored. If the installation is ° d ONLN dˇˇ * Vsuccessful, the Installer places a Cleanup INIT which deletes the temporary folder and ° d ONLN dˇˇ * ]it's contents at startup. Adding a 100 byte resource, may require 2M or greater of hard disk ° d ONLN dˇˇ * Zmemory on the boot volume. For this reason, it is difficult to perform an installation of ° d ONLN dˇˇ * Xsome System resource to a boot floppy. If the target volume is not a boot volume, these ° d ONLN dˇˇ * precautions are not performed. ° d ONLN dˇˇ ( ’ ~26. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+GRemoval from the active startup disk “^3” cannot take place while other ° d ONLN dˇˇ ( · êQapplications are running. Click Continue to automatically quit all other running ° d ONLN dˇˇ * 9applications. Click Cancel to leave your disk untouched. ° d ONLN dˇˇ *SThis alert occurs under System 7.0 when the removal will update files in the active ° d ONLN dˇˇ * XSystem Folder, and the Installer detects that there are open applications other than the ° d ONLN dˇˇ * %Finder or background processes. (59) ° d ONLN dˇˇ (- ~27. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+That disk is unreadable. ° d ONLN dˇˇ (A êMA floppy disk inserted during an Installer switch disk alert, was unreadable. ° d ONLN dˇˇ (U ~28. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+NAn error occurred while trying to complete the installation. Installation was ° d ONLN dˇˇ (a ê&canceled, leaving your disk untouched. ° d ONLN dˇˇ *XThis alert results when a resource problem occurs during a live install. The Installer ° d ONLN dˇˇ * \makes frequent checks of ResError during it's processing. It may encounter a spurious error ° d ONLN dˇˇ * Yset by some background process which gets interpreted as an unresolved Installer failure. ° d ONLN dˇˇ *YThe error has been found to occur with INITs which patch GetNextEvent in order to process ° d ONLN dˇˇ * ]specific system events. If this alert occurs, users should be advised to reboot their system ° d ONLN dˇˇ * Wwith the shift key held down under System 7.0, or to manually remove any suspect INIT's ° d ONLN dˇˇ * 8or other startup documents under System 6.0.x and prior. ° d ONLN dˇˇ (Ÿ ~29. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+SThe Installer needs to modify the file named “^0” on the disk “^3” but that file is ° d ONLN dˇˇ ( ê.locked. Please unlock the file and try again. ° d ONLN dˇˇ *VDepending on the scriptwriter’s wishes, the Installer will not overwrite locked files. ° d ONLN dˇˇ * SUnfortunately, if several files are locked, this alert occurs for each locked file. ° d ONLN dˇˇ ( ~30. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+GThe Installer found an alias named “<AliasName>” but could not find the ° d ONLN dˇˇ (% êToriginal Installer document to which this alias points. Make sure you are using the ° d ONLN dˇˇ * original Installer disks. ° d ONLN dˇˇ *VAn alias to an Installer script can be used in place of the actual document when using ° d ONLN dˇˇ * Bfloppy disks. If the alias cannot be resolved, this alert occurs. ° d ONLN dˇˇ (e ~31. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+PInstaller documents cannot be printed. Quit the Installer and open the document ° d ONLN dˇˇ (q êto do an installation. ° d ONLN dˇˇ *XThe user has tried to print the document using the Finder. The Installer may or may not ° d ONLN dˇˇ * already be running. ° d ONLN dˇˇ (• ~32. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+OThe files needed for this installation could not be found on your server volume ° d ONLN dˇˇ (± êL"<VolName>". Please contact your network administrator about this problem. ° d ONLN dˇˇ *^This error occurs when a network installation is run, and an error occurs accessing the source ° d ONLN dˇˇ * Zfiles. For example move some of the necessary files from the network installation folder, ° d ONLN dˇˇ * and attempt the installation. ˇB¥ d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ô ~#Installer Error and Message Strings , Palatino (Ô10
° d ONLN dˇˇ ( U ~33. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QProblems were encountered deleting old files. Please quit the Installer, restart ° d ONLN dˇˇ ( a ê3your Macintosh and try running the Installer again. ° d ONLN dˇˇ *WThis problem occurs when the Installer is unable to modify a target document. On a non ° d ONLN dˇˇ ( u- ° d ONLN dˇˇ ( Å êPboot volume installation, an open application may have some file opened which is ° d ONLN dˇˇ * Ytargeted for replacement by the installation. For example use ResEdit to open the System ° d ONLN dˇˇ * Mfile on a non-boot volume, and try to install system software to that volume. ° d ONLN dˇˇ ( ≠ ~34. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+NThe Installer document “<InstDoc>” is unusable for installation. An error was ° d ONLN dˇˇ ( π êZdetected before installation began. Make sure you are using the original Installer disks. ° d ONLN dˇˇ *[This error occurs when the Installer is unable to find a required resource specified in the ° d ONLN dˇˇ * ^installer script - 'inrl', 'inpk', 'infa', etc., has become corrupted, or the resource map has ° d ONLN dˇˇ * become corrupted. ° d ONLN dˇˇ *EThis error has also been known to occur due to the following reasons. ° d ONLN dˇˇ *U1. Two packages are included for installation which involve conflicting actions. One ° d ONLN dˇˇ * ^package calls for the installation of a file or resource, and the other package calls for it's ° d ONLN dˇˇ * deletion, if it exists. ° d ONLN dˇˇ *Z2. The same source resource is specified for installation as two different resources under ° d ONLN dˇˇ * ]separate resource ID's. In other words, there are 2 'inra' resource which reference the same ° d ONLN dˇˇ * 8source resource, but specify different target resources.
ˇˇ ˇˇ ˇˇ ˇˇ˚ ˇˇ ˇˇ ˇˇ˝ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˛ ¸ˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ ˛ˇ¸ ˇˇ˝ ¸ˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇfl ˇH˜zˇ Ê ˇH˜zˇØ ˛ˇ˛ ˇˇ ˇˇ ˇˇ˝ ˚ˇ˚ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˚ ˇˇ ˇˇ ˇˇ˝ ˚ˇ˚ ˇˇ ˇˇ˛ ˛ˇ˛ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ ˚ˇ˚ ˇˇ ˇˇ ˇˇ˝ !ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ˛ ˛ˇ˝ ˇˇ˛ ˇˇ ˇˇ ˇˇ ˇˇ ˚ˇ ˇˇfl ˇH˜zˇ Ë ˇH˜zˇÆ ˛ˇ ˇˇ ˇˇ ˇˇ˝ ˇˇ˜ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˚ ˇˇ ˇˇ ˇˇ˝ ˇˇ˜ ˇˇ ˇˇ˝ ˛ˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ ˇˇ˜ ˇˇ ˇˇ ˇˇ˝ !ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ˝ ˛ˇ˛ ˇˇ˛ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˚ ˇˇfl ˇH˜zˇ ˇ ˇH˜zˇ∞ ˇ ˇˇ ˇˇ ˇˇ ˇˇ˝ ˇˇ˛ ˇ˚ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˚ ˇˇ ˇˇ ˇˇ˝ ˇˇ˛ ˇ˚ ˇˇ ˇˇ ˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ ˇˇ˛ ˇ˚ ˇˇ ˇˇ ˇˇ˝ !ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ ˇ ˇˇ˛ ˇˇ˛ ˇˇ ˇˇ ˇˇ ˇˇ ˇˇ˛ ˇ ˇˇfl ˇH˜zˇ π ˇH˜zˇØ ˛ˇ˝ ¸ˇ ˇˇ¸ ˝ˇ˘ ¸ˇ˛ ˝ˇ˝ ¸ˇ˙ ¸ˇ ˇˇ¸ ˝ˇ˘ ¸ˇ˛ ˛ˇ˛ ˇˇ ˇˇ ˇˇ˛ ¸ˇ˘ ˇˇ ˇˇ ˇˇ˛ ˝ˇ˘ ˝ˇ˛ ˇˇ˝ ˇˇ˛ ¸ˇ ˇˇ ˇˇ ˇˇ˛ ¸ˇ ˇˇ˙ ˇˇ˛ ˇˇ ˇˇ˛ ˛ˇ¸ ˇˇ˛ ¸ˇ ˇˇ ˇˇ˛ ˝ˇ˛ ˇˇfl ˇH˜zˇ ˇH˜zˇã ˇˇ≤ ˇˇÀ ˇˇå ˇH˜zˇ + ˇH˜zˇè ˇ˛ ˇˇ∂ ˇ˛ ˇˇœ ˇ˛ ˇˇå ˇH˜zˇ ˇH˜zˇé ˝ˇ¥ ˝ˇÕ ˝ˇã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ " ˇH˜zˇ¨ ˇˇ ˇˇ¯ ˇˇÅ Å Ò ˇH˜zˇ ˇH˜zˇ¨ ˇˇÙ ˇˇÅ Å Ò ˇH˜zˇ . ˇH˜zˇØ ¸ˇ ˇˇ˛ ˛ˇ˛ ˇˇ ˇˇ˛ ˛ˇÅ Å ˚ ˇH˜zˇ 7 ˇH˜zˇ∞ ˇˇ ˇˇ ˇˇ ˇˇ ˇ ˇˇ ˇˇ˛ ˇˇ ˇÅ Å ¸ ˇH˜zˇ - ˇH˜zˇ∞ ˇˇ ˇˇ ˇˇ ˛ˇ˝ ˝ˇ˝ ˛ˇÅ Å ˙ ˇH˜zˇ - ˇH˜zˇ∞ ˇˇ ˇˇ ˇˇ˛ ˛ˇ˛ ˛ˇ˚ ˛ˇÅ Å ˚ ˇH˜zˇ . ˇH˜zˇ∞ ˇˇ ˇˇ ˇˇ˝ ˛ˇ ˝ˇ˚ ˛ˇÅ Å ¸ ˇH˜zˇ : ˇH˜zˇ∞ ˇˇ ˇˇ ˇˇ ˇ ˇˇ ˇˇ ˇˇ˛ ˇ ˇˇ ˇˇÅ Å ˇH˜zˇ 2 ˇH˜zˇØ ¸ˇ ˇˇ˛ ˛ˇ˛ ˇˇ ˇˇ˛ ˛ˇ˛ ˇˇÅ Å ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å È ≥ˇÒ ˇH˜zˇ ˇH˜zˇÅ Å Î ØˇÛ ˇH˜zˇ ˇH˜zˇÅ Å Ï ≠ˇÙ ˇH˜zˇ ˇH˜zˇÅ Å Ì ¸ˇµ ¸ˇı ˇH˜zˇ ˇH˜zˇÅ Å Ì ˛ˇ˛ ∑ˇ˛ ˛ˇı ˇH˜zˇ $ ˇH˜zˇÅ Å Ó ˝ˇ ˇˇ∑ ˇˇ ˝ˇˆ ˇH˜zˇ $ ˇH˜zˇÅ Å Ó ˛ˇ ˇµ ˇ ˛ˇˆ ˇH˜zˇ " ˇH˜zˇÅ Å Ó ˛ˇ ˇ≥ ˇ ˛ˇˆ ˇH˜zˇ " ˇH˜zˇÅ Å Ó ˛ˇ ˇ≥ ˇ ˛ˇˆ ˇH˜zˇ 0 ˇH˜zˇÅ Å Ó ˛ˇ ˇ· ˝ˇ˛ ˇˇ˛ ˇˇ· ˇ ˛ˇˆ ˇH˜zˇ 3 ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚
ˇˇ ˇˇ ˇˇ ˇˇ‡ ˇ ˛ˇˆ ˇH˜zˇ 2 ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚ ˇˇ ˇˇ ˇˇ ˇˇfl ˇ ˛ˇˆ ˇH˜zˇ / ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚ ˇˇ ˇˇ ˝ˇfi ˇ ˛ˇˆ ˇH˜zˇ / ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚ ˇˇ ˇˇ ˛ˇ› ˇ ˛ˇˆ ˇH˜zˇ / ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚ ˇˇ ˇˇ ˝ˇfi ˇ ˛ˇˆ ˇH˜zˇ 2 ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚ ˇˇ ˇˇ ˇˇ ˇˇfl ˇ ˛ˇˆ ˇH˜zˇ 3 ˇH˜zˇÅ Å Ó ˛ˇ ˇ‚
ˇˇ ˇˇ ˇˇ ˇˇ‡ ˇ ˛ˇˆ ˇH˜zˇ 0 ˇH˜zˇÅ Å Ó ˛ˇ ˇ· ˝ˇ˛ ˇˇ˛ ˇˇ· ˇ ˛ˇˆ ˇH˜zˇ " ˇH˜zˇÅ Å Ó ˛ˇ ˇ≥ ˇ ˛ˇˆ ˇH˜zˇ " ˇH˜zˇÅ Å Ó ˛ˇ ˇ≥ ˇ ˛ˇˆ ˇH˜zˇ " ˇH˜zˇÅ Å Ó ˛ˇ ˇ≥ ˇ ˛ˇˆ ˇH˜zˇ $ ˇH˜zˇÅ Å Ó ˛ˇ ˇµ ˇ ˛ˇˆ ˇH˜zˇ $ ˇH˜zˇÅ Å Ó ˝ˇ ˇˇ∑ ˇˇ ˝ˇˆ ˇH˜zˇ ˇH˜zˇÅ Å Ì ˛ˇ˛ ∑ˇ˛ ˛ˇı ˇH˜zˇ ˇH˜zˇÅ Å Ì ¸ˇµ ¸ˇı ˇH˜zˇ ˇH˜zˇÅ Å Ï ≠ˇÙ ˇH˜zˇ ˇH˜zˇÅ Å Î ØˇÛ ˇH˜zˇ ˇH˜zˇÅ Å È ≥ˇÒ ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zˇÅ Å ã ˇH˜zˇ ˇH˜zÅˇÅˇâˇH˜zˇ ˇH˜zÅHÅHàH˜zˇ ˇHŘŘ֘zˇ ˇÅzÅzÉzˇ
ÅˇÅˇÅˇ Ì ÅˇÅˇ ˇ∫ ˇÌ
_ ° d ONLN dˇˇ ( ~35. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+MA disk error has occurred and installation cannot continue. Your disk may be ° d ONLN dˇˇ (# êdamaged. ° d ONLN dˇˇ *VThis error occurs when the Installer and/or script file are placed on an MFS formatted ° d ONLN dˇˇ * *diskette, and are used from that diskette. ° d ONLN dˇˇ (W ~36. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+GThe Installer needs to create a folder named “<FolderName>” on the disk ° d ONLN dˇˇ (c êW“<DiskName>” but a file with this name already exists. Please rename this file or move ° d ONLN dˇˇ * it to another folder. ° d ONLN dˇˇ *WThe Installer is unable to create some folder because a file exists by that name in the ° d ONLN dˇˇ * specified locations. ° d ONLN dˇˇ (£ ~37. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+CThe file “<FileName>” on disk “<DiskName>”cannot be replaced by the ° d ONLN dˇˇ (Ø ê\Installer. No installation will take place. Please move the file to another folder and try ° d ONLN dˇˇ * again. ° d ONLN dˇˇ *\This alert is related to the previous error except that a folder by the same name as that of ° d ONLN dˇˇ * >the file exists on the target pathname and cannot be replaced. ˇ≤ d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ô ~#Installer Error and Message Strings , Palatino (Ô11
° d ONLN dˇˇ ( U êVAnother reason for this error is when the creation date/time field for the target (not ° d ONLN dˇˇ * Zsource) file specification resource, 'infs' is non-zero AND the file already exists in the ° d ONLN dˇˇ * Wspecified location. The Programmer's Guide indicates that the creation date/time field ° d ONLN dˇˇ * \should be zero. In fact, it must be set to zero, otherwise this alert occurs when trying to ° d ONLN dˇˇ * 4perform a second installation to a target hard disk. ° d ONLN dˇˇ *WThis error also occurs if the target file specification has specified "typeCrMustMatch" ° d ONLN dˇˇ * [and the type and creator of the actual target file do not match the specified values in the ° d ONLN dˇˇ * target file specification. ° d ONLN dˇˇ ( ≈ ~38. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+JThe Installer cannot copy the file “<FileName>” onto the disk “<DiskName>” ° d ONLN dˇˇ ( — ê[Installation cannot continue. Please delete this file and try running the Installer again. ° d ONLN dˇˇ *_This error occurs when the Installer runs into problems copying a target file, but not for the ° d ONLN dˇˇ * ]reason that a folder exists by the same name as the file. Instead, the file copy process has ° d ONLN dˇˇ * /already begun, however, it cannot be completed. ° d ONLN dˇˇ *SOne unusual situation which can lead to this problem occurs when one user sets up a ° d ONLN dˇˇ * Unetwork installation and turns personal file sharing on. A second user then turns on ° d ONLN dˇˇ * \personal file sharing then mounts the first users server with administrator, while the first ° d ONLN dˇˇ * Zuser mounts the second users volume. The second user launches the network installation to ° d ONLN dˇˇ * Yinstall software onto his volume. If the first user can lock a newly created file on the ° d ONLN dˇˇ * Osecond users disk while the Installer is creating the file, this alert results. ° d ONLN dˇˇ (a ~39. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+H“<FileName>” cannot run on this model of Macintosh. Please contact your ° d ONLN dˇˇ (m êWauthorized Apple dealer and inquire about upgrading your hardware. Click Quit to leave ° d ONLN dˇˇ * the Installer. ° d ONLN dˇˇ *_This error occurs when trying to use the Installer on a 128K or 512K Mac. Installer 3.4 is not ° d ONLN dˇˇ * compatible with these Systems. ° d ONLN dˇˇ (≠ ~40. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KThe Installer document “<InstDoc>” is damaged. Make sure you are using the ° d ONLN dˇˇ (π ê'original Installer disks and try again. ° d ONLN dˇˇ *UThe script document cannot be opened by the Installer. This error can result given a ° d ONLN dˇˇ * Tnetwork installation when the administrator launches the script locally, then a user ° d ONLN dˇˇ * ]accesses the script from a workstation and tries to run the script using a remote copy of the ° d ONLN dˇˇ * FInstaller. The workstation Installer will receive this alert message. ° d ONLN dˇˇ *ZAnother possible reason is that not enough memory is available to load the script into the ° d ONLN dˇˇ * PInstaller’s heap. Try raising the Installer’s partition if the script is large. ° d ONLN dˇˇ (% ~41. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+KAn error occurred while removing. Removal was not able to be completed, but ° d ONLN dˇˇ (1 ê)your original software has been restored. ° d ONLN dˇˇ *YAn unspecified error occurred while doing software removal from the boot-disk. The error ° d ONLN dˇˇ * Xcan occur from incompatible startup documents or INIT's. To overcome, reboot the system ° d ONLN dˇˇ * Zwith the shift key held down under System 7.0 or greater, or remove all extraneous startup ° d ONLN dˇˇ * >documents and INITs and reboot under System 6.0.x and earlier. ° d ONLN dˇˇ (} ~42. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )++An unknown error #"<Error #>" has occurred. ° d ONLN dˇˇ (ë êWThis is a catch all error alert which appears when an error occurs during some phase of ° d ONLN dˇˇ * Xinstallation which the Installer cannot sort out. The two common error numbers are 2231 ° d ONLN dˇˇ * Wand 2232. Error 2231 indicates that some resource file could not be found. Error 2232 ° d ONLN dˇˇ * \indicates that a specific resource could not be found. Both of these errors have been found ° d ONLN dˇˇ * Uto occur as a result of incompatible startup documents or INITs. The Installer makes ° d ONLN dˇˇ * Ufrequent checks of ResError and may encounter a spurious error set by some background ° d ONLN dˇˇ * Bprocess which gets interpreted as an unresolved Installer failure. ˇ§ d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ô ~#Installer Error and Message Strings , Palatino (Ô12
° d ONLN dˇˇ ( U êYThe error has been found to occur with INITs which patch GetNextEvent in order to process ° d ONLN dˇˇ * ]specific system events. If this alert occurs, users should be advised to reboot their system ° d ONLN dˇˇ * Wwith the shift key held down under System 7.0, or to manually remove any suspect INIT's ° d ONLN dˇˇ * 8or other startup documents under System 6.0.x and prior. ° d ONLN dˇˇ ( ç ~43. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+=A clean install cannot be performed on the disk “<DiskName>”. ° d ONLN dˇˇ ( ° êWThis error is displayed when trying to setup a clean install using the Command-Option-K ° d ONLN dˇˇ * Wkeys, when a clean install is inappropriate. This might be because: no blessed folder ° d ONLN dˇˇ * aexists on the target disk, the preference flag is set to not allow clean installs, or an internal ° d ONLN dˇˇ * 8error occurred while setting up the clean install. (18) ° d ONLN dˇˇ ( Ÿ ~44. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+JThere are too many desk accessories on “^3” to complete this installation. ° d ONLN dˇˇ (  êXInstallation would result in ^0 desk accessories; only ^1 are allowed. Remove some desk ° d ONLN dˇˇ * accessories, and try again. ° d ONLN dˇˇ *QWhen installing a desk accessory as a ‘DRVR’ resource in the System this error is ° d ONLN dˇˇ * 1displayed if all DA driver slots are taken. (26) ° d ONLN dˇˇ (% ~45. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+TThe disk “^0” could not be ejected because it is being shared. Please turn off file ° d ONLN dˇˇ (1 ê'sharing and try the installation again. ° d ONLN dˇˇ *YThe Installer displays with error when trying to eject a CD-ROM to make room for the user ° d ONLN dˇˇ * Zto insert another CD-ROM, but the File Manager returned an error when calling Eject. (48) ° d ONLN dˇˇ (e ~46. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QInstaller documents cannot be opened while the Installer is running. Please quit ° d ONLN dˇˇ (q ê*the Installer and open the document again. ° d ONLN dˇˇ *XThe user has tried to open the document using the Finder while the Installer is running. ° d ONLN dˇˇ * JInstaller documents can only be opened when launching the Installer. (78) ° d ONLN dˇˇ (• ~47. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThe file “^0” on the disk “^3” is too large to accommodate the installation. The ° d ONLN dˇˇ (± êFinstallation cannot continue. Try removing “^0” and installing again. ° d ONLN dˇˇ *ZThe script is adding resources or fonts to a file whose resource fork will exceed the 16Mb ° d ONLN dˇˇ * Xsize limit. This was a real issue when installing Kanji fonts into the System file, but ° d ONLN dˇˇ * >shouldn’t happen as often with separate font suitcases. (79). ° d ONLN dˇˇ (Ò ~48. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+SThe installation cannot continue because the source file “^0” on the disk “^1” will ° d ONLN dˇˇ (˝ ê\be overwritten during the installation. Please choose a different installation disk and try ° d ONLN dˇˇ * again.. ° d ONLN dˇˇ *]The Installer will write over a file that is part of the installation sources. For disk mode ° d ONLN dˇˇ * only. (80) ° d ONLN dˇˇ (= ~49. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+SThe installation cannot continue because the source file “^0” on the disk “^1” will ° d ONLN dˇˇ (I êZbe overwritten during the installation. Please select a different installation folder and ° d ONLN dˇˇ *
try again. ° d ONLN dˇˇ *ZThe Installer will write over a file that is part of the installation sources. For folder ° d ONLN dˇˇ * mode only. (81) ° d ONLN dˇˇ (â ~50. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThe removal cannot continue because the source file “^0” on the disk “^1” will be ° d ONLN dˇˇ (ï êQdeleted during the removal. Please choose a different target disk and try again. ° d ONLN dˇˇ *_The Installer will delete a file that is part of the installation sources. For disk mode only. ° d ONLN dˇˇ * (82) ° d ONLN dˇˇ (… ~51. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThe removal cannot continue because the source file “^0” on the disk “^1” will be ° d ONLN dˇˇ (’ êSdeleted during the removal. Please select a different target folder and try again. ˇñ d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ô ~#Installer Error and Message Strings , Palatino (Ô13
° d ONLN dˇˇ ( U ê[The Installer will delete a file that is part of the installation sources. For folder mode ° d ONLN dˇˇ * only. (83) ° d ONLN dˇˇ ( u ~52. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+OCannot overwrite a protected resource in the file “^0” on the disk “^3”. Error ° d ONLN dˇˇ ( Å ê#detected before installation began. ° d ONLN dˇˇ *WA resource specified for replacement on the target disk has the protected bit set. The ° d ONLN dˇˇ * Fprotected bit needs to be cleared before the installation can proceed. ° d ONLN dˇˇ ( µ ~53. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+LThe selected disk is too full. Please remove some files you no longer need. ° d ONLN dˇˇ ( … êVThis problem can occur when the target volume is being shared via File Sharing. If an ° d ONLN dˇˇ * \installation is started and a user logs onto the same disk and copies additional data to the ° d ONLN dˇˇ * Yserver after the Installer preflight has taken place, the target disk may run out of hard ° d ONLN dˇˇ * #disk space resulting in this error.
° d ONLN dˇˇ ( 6 Other Installer Error Alerts " ° ∂ 4 + ° ∂ ° ∂
° d ONLN dˇˇ +HZThe following Installer Alert messages can appear during an installation. Where possible, ° d ONLN dˇˇ * Ztroubleshooting is provided. Unfortunately, comprehensive information is not available at ° d ONLN dˇˇ *
this time. ° d ONLN dˇˇ * 1. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThere is a problem with the source disk “^0”. Installation cannot continue. The ° d ONLN dˇˇ (n êUpartially installed software may not be usable. Make sure you are using the original ° d ONLN dˇˇ * Installer disks. ° d ONLN dˇˇ *XThe Installer received a Resource Manager error while trying to read from a source file. ° d ONLN dˇˇ * RThis error has been found to occur with INITs which patch GetNextEvent in order to ° d ONLN dˇˇ * ^process specific system events. If this alert occurs, users should be advised to reboot their ° d ONLN dˇˇ * Wsystem with the shift key held down under System 7.0, or to manually remove any suspect ° d ONLN dˇˇ * ?INIT's or other startup documents under System 6.0.x and prior. ° d ONLN dˇˇ (“ ~2. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+JA problem occurred with the AppleTalk network. Please quit the Installer, ° d ONLN dˇˇ (fi ê<restart your Macintosh, and try running the Installer again. ° d ONLN dˇˇ *RThe network connection may have gone down while performing a network installation. ° d ONLN dˇˇ ( ~3. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+:A necessary file is locked. Installation cannot continue. ° d ONLN dˇˇ ( ê[The Installer received the File Manager error -54 or -45 while opening a target file. Most ° d ONLN dˇˇ * Jlikely, something or someone locked a target file during the installation. ° d ONLN dˇˇ (: ~4. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThere are too many files open on your Macintosh. Please quit the Installer, quit ° d ONLN dˇˇ (F ê9any other applications you may be running, and try again. ° d ONLN dˇˇ *ZThe Installer received the File Manager error -42 while opening a file. This might be the ° d ONLN dˇˇ * Vcase if another application has numerous files open, that would cause the Installer to ° d ONLN dˇˇ * Zreach the maximum number of files that can be open at once. Try using up all but two FCBs ° d ONLN dˇˇ * (then performing a non-live installation. ° d ONLN dˇˇ (í ~5. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+NThere is a problem with the source disk “^0”. No installation can take place. ° d ONLN dˇˇ (û ê5Make sure you are using the original Installer disks. ° d ONLN dˇˇ *FThe Installer received an error while examining the first source disk. ° d ONLN dˇˇ (Δ ~6. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+O“<Installer>” cannot run on your version of Macintosh Software. Please restart ° d ONLN dˇˇ (“ êVyour Macintosh using your original set of distribution disks. Click Quit to leave the ° d ONLN dˇˇ *
Installer. ˇŒ d ˇ ˇˇˇˇ d
_ , Helvetica
. (Ô ~#Installer Error and Message Strings , Palatino (Ô14
ê/Macintosh, and try running the Installer again. ° d ONLN dˇˇ *WWe may display this error when the File Manager returns an error of -53. This error may ° d ONLN dˇˇ * -be converted into a more generic error. (10) ° d ONLN dˇˇ (A ~14. ° d ONLN dˇˇ ) Message: ° d ONLN dˇˇ )+QThere is a problem with a disk you are installing onto. No installation can take ° d ONLN dˇˇ (M ê)place. Try installing onto another disk. ° d ONLN dˇˇ *ZResource Manager errors were returned during opening, reading or writing a target resource ° d ONLN dˇˇ * Jor font. Most likely, the target file’s resource fork is corrupted. (47) ˇ
